Closed
Conversation
Contributor
|
The hash of the file needs to be updated. (see #545 ) |
Contributor
|
Normally the hash only should need updating if rust-toolchain.toml changes, and the new hash is what nix says it has gotten (example). It goes here. But that's only if you want to fix it yourself in the same PR where rust-toolchain.toml changes, otherwise some nix people will surely fix it soon enough 😄 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There seems to be a weird hash conflict with the Nix workflow since bumping
rust-toolchain.tomlto be1.88, so I'm going to try1.89to see if that fixes the issue.